| "What you are not seeing is that when the system enters safety mode, it reads from the low octane fuel map and low octane ignition timing map. In the JWT programs that I have seen, both the high octane (nonsafety maps) and low octane (safety maps) are identical. What this means is when the system tries to save your engine by reverting to what should be a fuel map with more fuel delivery and a timing map with less advanced timing, it simply finds maps that are the same as the high octane counterparts." So here you are saying that the JWT programs that YOU have seen do not retard the timing when safety boost is in effect?? I have seen it work on JWT's program so I find this hard to believe. The funny thing is below you say just the opposite. "Since I have a boost control system (no jets), I couldn't feel that it was in safety boost other than the fact that the performance was suffering. But because my own program, which I run in my own car, does have low octane maps that are in fact, properly setup, I could feel the drop in performance and it keyed off in my mind, "Hey, it may be throwing a code." I wouldnt' have known this was the case if I were using a JWT program. That's all my post was about." OK again as I read it you are saying that the JWT program does NOT retard timing when detonation is sensed but YOUR program does and that is what you felt in the lack of power. Again lets read this next statement where you totally contradict yourself. "What you are thinking of is when timing gets kicked back when detonation is sensed. Sure, both stock and JWT's program do that. So does mine. It is part of the knock sensing subroutine. When the ECU is accessing the region of the map in red, it is listening for knock." WTF?? "Sure, both stock and JWT's program do that. So does mine." So if it does retard the timing like YOUR program....How is it less safe???? First you say it doesn't and now it does....which is it??? "In this program, it only listens for knock up to 3200RPM at its highest load (furthest left column). IF it detects knock here, it will retard timing, but ONLY in this region. Peak VE, where detonation is most likely to occur, is well beyond 3200RPM. A dyno chart will tell you where your peak VE is (peak torque), and for most that happens around 4500RPM." That is a setup in the stock ECU. Since both your program and JWT use the stock ECU and the stock sensors how is YOUR program going to be safer since you just said above that your program AND JWT's program both retard the timing when the detonation sensor senses detonation under 3200RPM???? I just don't get the point of the first post. You are saying your program is safer but your program and JWT's program both use the LOW octane map and retard the timing when detonation is sensed through the stock detonation sensor. Now I hope you are not trying to say that JWT advances the timing in the low octane map and has NO features to go into safety boost. I have seen this with my own eyes so I know that is not true.
Kyle "Grumpy Bear" Puckett
ICQ #727815 
 |
10:34:57 01/15/03
